Changes between Version 40 and Version 41 of Using Pidgin

Timestamp:

Jun 17, 2007, 9:56:12 PM (17 years ago)

Author:

cwal

Comment:

spelling

Using Pidgin

@@ -119 +119 @@
 
 === Can I "skin" Pidgin? ===
-The UI can be customized using GTK themes and by [wiki:SmileyThemes Smiley Themes].  Application-specific skins will never be supported Pidgin.  This seems to confuse a lot of users, so here's an attempt at an explanation.  (In addition, skinning a pidgin (pigeon) would kill it, another reason it isn't supported.)
-
-Themes allow you to change font size, font face, the color of different elements of the UI, and sometimes their shape. All of this is perfectly reasonable, and encompasses the range of configuration that ''most'' users are requesting. Skins go beyond this. Skins allow you to move and possibly supress different elements of the UI that the programmers have added for specific reasons.
+The UI can be customized using GTK themes and by [wiki:SmileyThemes Smiley Themes].  Application-specific skins will never be supported by Pidgin.  This seems to confuse a lot of users, so here's an attempt at an explanation.  (In addition, skinning a pidgin (pigeon) would kill it, another reason it isn't supported.)
+
+Themes allow you to change font size, font face, the color of different elements of the UI, and sometimes their shape. All of this is perfectly reasonable, and encompasses the range of configuration that ''most'' users are requesting. Skins go beyond this. Skins allow you to move and possibly suppress different elements of the UI that the programmers have added for specific reasons.
 
 In so doing, skins create a support nightmare. The developer, talking to the user, cannot be sure that the user sees the same interface. Is it a bug that the user cannot see how to change font size, or is the user's skin suppressing that widget? This is an unacceptable situation.
 
-Conversely, while themes allow some sillyness, for instance setting the background to the same color as the font, the results are relatively easily foreseen and avoided by theme authors. Further, by using the existing GTK theme mechanism, we gain two advantages:
+Conversely, while themes allow some silliness, for instance setting the background to the same color as the font, the results are relatively easily foreseen and avoided by theme authors. Further, by using the existing GTK theme mechanism, we gain two advantages:
   1. We don't have to write it ourselves.  Were we to write our own mechanism, we would be adding overhead in both the run time and the time necessary to debug.
   1. We have a built in way of debugging theme problems, by checking if the same bug exists with other GTK programs.
@@ -301 +301 @@
 It is not possible to make Pidgin translucent in Linux and other platforms that use X11.
 
-The X.org X11R6 server provides a COMPOSITE extension that allows applications to have true translucency, but it is X.org-specific and it requires support at the GTK+ level (if it is to be per-widget).  We do not wish to support this form of translucency until it is supported by GTK+.  We also do not wish to implement the psuedo-translucency offered by other programs (by copying a section of your background image, tinting it, and plastering it onto a Pidgin window).
+The X.org X11R6 server provides a COMPOSITE extension that allows applications to have true translucency, but it is X.org-specific and it requires support at the GTK+ level (if it is to be per-widget).  We do not wish to support this form of translucency until it is supported by GTK+.  We also do not wish to implement the pseudo-translucency offered by other programs (by copying a section of your background image, tinting it, and plastering it onto a Pidgin window).